5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
+ Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
- Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-8: Runtime Subroutine's and Predefined Processes

.UTIL CHECK SECURITY


This subroutine is called to check the security code for the specified user.

Usage:

Description:

This subroutine is called to check the security code for the specified user. All parameters are required, except for <oper_phase>. If any required parameters are missing, the subroutine will CANCEL.

<result> will contain Y or N, depending on the setting of the specified security code (Required). This must be PASSed Share "Y" to return the value.

<sec_class> is the security class to be tested, from 1-9999 (Required).

<user_id> is the user to be tested (Required).

<database_id> is the database to be tested (Required).

<oper_phase> is the operational phase to be tested (Optional). If not passed, it will default to the operational phase of the current application. If passed, it must be one of Live Operations, Initial Set Up or Recovery Processing.

If you are using Role Based Security, use .UTIL CHECK RBS instead.

Application Design Manual                                         "Powered by Appx Software"

1169

©2006 By APPX Software, Inc. All Rights Reserved